Skip to content

fix: handle npm 12 registry misses - #21

Merged
witqq merged 1 commit into
masterfrom
fix/npm12-registry-preflight
Sep 5, 2026
Merged

fix: handle npm 12 registry misses#21
witqq merged 1 commit into
masterfrom
fix/npm12-registry-preflight

Conversation

@witqq

@witqq witqq commented Sep 5, 2026

Copy link
Copy Markdown
Owner

Summary

  • treat an npm registry miss by the npm view exit status instead of parsing its npm 12 JSON error object as a URL
  • require every successful dist.tarball response to be a valid HTTPS URL
  • add a regression assertion that forbids the previous error-swallowing pattern

Verification

  • actionlint .github/workflows/ci.yml .github/workflows/publish-npm.yml
  • npm run check:workflows
  • git diff --check

No npm package version was published by the failed run. The existing v0.6.0 GitHub Release assets remain unchanged and will be reused after merge.

Made with Moira

Use npm view exit status for coordinated publication preflight and reject non-URL registry responses.
@witqq
witqq merged commit 6ad7c3f into master Sep 5, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant